翻訳と辞書
Words near each other
・ Test-and-set
・ Test-driven development
・ Test-Driven Development by Example
・ Testa
・ Testa (surname)
・ Testa del Leone
・ Testa del Rutor
・ Testa Grigia
・ Testa Grigia (Aosta Valley)
・ Testa Ridge
・ Testa, Hurwitz & Thibeault
・ Testability
・ Testaccio
・ Test driver
・ Test effort
Test engineer
・ Test Environment Management
・ Test equipment
・ Test execution engine
・ Test film
・ Test fixture
・ Test Flight and Development Centre SAAF
・ Test for Echo
・ Test for Echo (song)
・ Test for Echo Tour
・ Test functions for optimization
・ TeST Gliders
・ Test harness
・ Test Icicles
・ Test in Swedish for University Studies


Dictionary Lists
翻訳と辞書 辞書検索 [ 開発暫定版 ]
スポンサード リンク

Test engineer : ウィキペディア英語版
Test engineer
A hardware test engineer is a professional who determines how to create a process that would best test a particular product in manufacturing, quality assurance or related areas, like the RMA department, in order to assure that the product meets applicable specifications. Test engineers are also responsible for determining the best way a test can be performed in order to achieve 100% test coverage of all components using different test processes. Often Test Engineers also serve as a liaison between manufacturing, Design Engineering, and Field Engineering (Customer Service) communities as well.
Test engineers can have different expertise which depends on what test process they are more familiar with (although many test engineers have full familiarity from the PCB level processes like ICT, JTAG, and AXI) to PCBA and system level processes like board functional test (BFT or FT), burn-in test, system level test (ST). Some of the processes used in manufacturing〔()〕 where a test engineer is needed are:
* In-circuit test (ICT)
* Stand-alone JTAG test
* Automated x-ray inspection (AXI) (also known as X-ray test)
* Automated optical inspection (AOI) test
* Continuity or flying probe test
* (Board) functional test (BFT/FT)
* Burn-in test
* Environmental stress screening (ESS) test
* Highly Accelerated Life Test (HALT)
* Highly accelerated stress screening (HASS) test
* Ongoing reliability test (ORT)
* System test (ST)
* Final quality audit process (FQA) test
==Early project involvement from design phase==

Ideally, a test engineer's involvement with a product begins with the very early stages of the design phase. Depending on the culture of the firm, the early stages could refer to Product Requirements Document (PRD) and Marketing Requirements Document (MRD)—some of the earliest work done during a new product introduction (NPI).
By working with or as part of the NPI group, a test engineer ensures that a product is designed for both testability and manufacturability. In other words, to make sure that the product can be readily tested and built.
The following are some general rules to ensure testability and manufacturability of a product:
* Making sure the product has correct label specs and placement that would make it possible for the unit to be traceable and programmable. Implementing good label specs results in having correct information programmed correctly into the unit under test (UUT) (sometimes called DUT or device under test). To make this possible, the test engineers enforce those labels location and are all readable and scannable, thus eliminating the need for a manual typing of information into the unit. Automatic placing of identification codes into the part during test and making them available for verification at later processing steps can help minimize these types of errors. Manual typing can introduce problems related to inaccurate information being programmed due to human errors. Also, without the test engineers input during PRD design phase, the hardware engineer in charge of designing of the silk-screen for the PCB may put those labels below some attachable board which will then later renders the labels useless (i.e. in a motherboard/daughterboard design and also a board that has a pluggable module, a label would be visible on the main board by itself but would be obstructed by the other boards that needs to be integrated). This information are often indicated in both PRD and MRD.
* Making sure that all components required to test and debug the UUT, which includes the console/serial port, are all accessible from the early part of the manufacturing process up to the last part which is often the final quality audit/assurance (FQA) process. This also includes making sure those components are available even after the units are returned by the customers for troubleshooting or repair. By following this guidelines, the team will eliminate unnecessary opening of the UUT just to access those components which may result in introducing errors into the unit (i.e. knocking off some capacitors or resistors when opening/sliding out the cover, dropping the tool inside the PCBA after opening, forgetting some other cables to reconnect before closing the unit for manufacturing process flow continuation, etc.).
* Making sure that all components needed to test the unit are added into the cost matrix of the final product. This components may include the UART/RS232 chips for talking to the UUT, ethernet ports for upgrading the firmware, JTAG connectors, etc.
* Defining what manufacturing test process is needed based from the product definition.
* Verifying that the currently available test equipment is adequate for testing the proposed design. If new equipment is needed, budgetary concerns have been addressed and sufficient lead time exists for new equipment installation and verification. Also, new test equipment may require training for test equipment operators and supervisors.
By following the general rules above, test engineers minimize future surprises (like adding extra components, re-layout of the boards, etc.) which drives up costs and development delays of the final product.

抄文引用元・出典: フリー百科事典『 ウィキペディア(Wikipedia)
ウィキペディアで「Test engineer」の詳細全文を読む



スポンサード リンク
翻訳と辞書 : 翻訳のためのインターネットリソース

Copyright(C) kotoba.ne.jp 1997-2016. All Rights Reserved.